Quick Beginnings

API Client Attachments

Support for Communications Server

If you are connecting to an IBM Communications Server for Windows by using the Communications Server client or installing on the Communications Server machine, configure Personal Communications to use the SNA API client interface.

The API client interface lets you make the following attachments:

• 3270 emulation

  LUA - LU 0, 1, 2 or 3 via the WinRUI interface. This lets you have normal display or printer sessions.

• APPC3270

  This provides 3270 display sessions (not printer) over an LU 6.2 connection to the host.

• 5250 emulation

  This provides 5250 display and printer sessions through APPC.

Note:

You must first install the Communications Server for Windows 5.0 or later client.

You can install Personal Communications on top of Communications Server for Windows Server or over the API Client.

Two interfaces are supported:

• Communications Server for Windows

  You can run Personal Communications on a Communications Server; it uses the Communications Server protocol stack to connect to the host.

• Client for Communications Server for Windows

  For client workstations, Communications Server has a client that communicates with the server and provides an interface that Personal Communications can use. The client must be installed on your workstation before you install Personal Communications.

Note:

You cannot install the Personal Communications SNA protocol drivers if you intend to use the API Client interface. You can, however, use the non-SNA attachment types, which include HPO, Home3270, TN3270, and IPX/SPX.

Load Balancing

Personal Communications supports load balancing for all client types. Load balancing enables you to distribute LU 0 to 3 and LU 6.2 sessions across Personal Communications servers. The server advertises services including load factors, which the clients or servers can gather and organize to select a server.

Load Balancing over TCP/IP Protocols

Load Balancing over TCP/IP protocols is a key feature for IBM Communications Server for Windows 5.1. This feature dynamically balances dependent LU2 (host-to-workstation) sessions. For LU2 sessions over TCP/IP connections, the load is distributed across servers within a named LU2 pool and a named scope. That is the server with the least overall load within the named scope supporting the named LU2 pool will satisfy a given LU2 connection request.

Notes:

1. IBMSLP.DLL should be available on the client workstation system directory. Refer to your Server documentation for information about where to obtain this dynamic load library file.

2. For true load balancing use a wild card ('*') Server Name and Service Name, and use the pooled LU category with a LU-Pool Name.

Hot Standby

The Hot Standby feature enables to ensure that configured connections to a host can continue to function when a critical server goes down by triggering activation of alternative connections on a backup server. Load Balancing can be used in conjunction with Hot Standby.

If the active session to the server goes down because of server or link failure, Personal Communications will try to reconnect the session with the provided backup server name, service name, or pool name.

IBMSLP.DLL should be available on the client workstation system directory.